Only import a portion of a code file delimited by VS Code custom regions markers, based on the region key you set via a fragment identifier (#):

/docs/hello-world.md

# Hello World

<<< @/src/hello-world.js#function-def{1-2}

/src/hello-world.js:

// #region function-def
function helloWorld () {
  // ..
}
// #endregion function-def

export default helloWorld

Motivation

Contents presented with Vuepress (documentation, tutorials, etc.) may (often?) be related to some "real" projects. Ensuring the code snippets in the doc and the "real" code is very important for this use case. Yet, it can be difficult, or even impossible, to split each code sample in a dedicated file. Therefore, some misleading code lines may be shown in the code snippet only because the author needs it in the project.

For example, if I want to show a function in the doc, but I need an export in order to use this function in my project, I would have to show it in the code snippet:

function foo () {
  // ...
}

export default foo;

Solution

This solution add support for:

• VS Code custom region markers
  • clearly indicate a region to import
  • why: a lot of web developers (and therefore, I guess, Vuepress users) use VS Code and should be familiar with this syntax
• fragment identifier (path#region)
  • indicate the name of the custom region to import
  • why: same logic as the one defined in the URL standard (see W3C doc)

For more details, see the new documentation and tests.

Compatibility

Does not introduce any breaking change: result stay exactly the same if no fragment identifier is set (no region name is set by default).
Yet, the new syntax isn't backward compatible: adding a fragment identifier to the path will lead to a "cannot find path @/path/file.ext#region" with the current version of Vuepress.

If you want to use this feature before this PR is merged, you can use patch-package as follow:

1. download patches.zip
2. extract this zip file in your project root (should create patches/@vuepress+markdown+1.3.1.patch)
3. add patch-package to your dev dependencies:

   npm i -D patch-package
   

   or

   yarn add --dev patch-package postinstall-postinstall
   

4. add patch-package in your postinstall script

   "scripts": {
   +  "postinstall": "patch-package"
   }
   

Summary

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Docs
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change? (check one)

• Yes
• No

The PR fulfills these requirements:

You have tested in the following browsers: (Providing a detailed version will be better.)

• Chrome 80.0.3987.132 Linux
• Firefox 74 Linux
• Safari
• Edge
• IE

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature
• Related documents have been updated
• Related tests have been updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.

Other information

This feature is already used on a daily basis for a pretty heavy (but private) project, alongside a related Pandoc filter which provides this feature: pandoc-import-code.